Webhook creation

Peculiarities

When creating an inspection (when the inspection is first recorded in the server database)

Coverage

The role of the owner of the webhook is taken into account (who created, that and the owner). Administrators are notified of all new company scans. Group Administrators – inspections of those access groups to which the group administrator belongs.

Peculiarities

At the time of creating an inspection in the database, no data is tied to it, except for the key determinants, such as: who created it, according to what template, for which company. For post-processing via the integration api, it is more convenient to use the "Inspection changed status" event.

Works

When the inspection was shared with another user via a mobile app, admin interface, or via the integration api.

Coverage

The role of the owner of the webhook is taken into account (who created, that and the owner). Administrators are sent messages about all company inspections. Group Administrators – information about inspections of those access groups to which the group administrator belongs.

Peculiarities

The person who shares the inspection indicates the recipient's full name and phone number. The system finds the recipient in the database, or creates a new user with the "client" role. In the notification data, we send information about both the recipient and who shared the inspection.

Works

When the server receives the first request to initialize a new shooting for inspection

Coverage

The role of the owner of the webhook is taken into account (who created, that and the owner). Administrators are sent messages about all company inspections. Group Administrators – notification about inspections from those access groups to which the group administrator belongs.

Peculiarities

We fix the moment when the user first came to photographing. This event can be considered the actual start of the inspection, since filling out the inspection form quite often does not mean that the user is going to photograph something. Keep in mind that the notification comes at the moment when the server receives data about the start of the shooting, and not at the moment of the start of the shooting as such. The user can be offline at this time.

Works

After installation, the new status will be examined (when the status is changed in the server database)

Coverage

The role of the owner of the webhook is taken into account (who created, that and the owner). Administrators are sent messages about all company inspections. Group Administrators – Changes to the statuses of inspections of those access groups to which the group administrator belongs.

Peculiarities

The notification uses status aliases, rather than their textual representation for users. Below are the statuses with their basic texts (personal texts can be set for assemblies – they are not taken into account here). The list can be expanded at a later time, do not lim it the variance on the receiving side to what is listed here.

• draft – inspection not completed, inspection started, inspection in progress

  sending – sending to server

  preexpertise – sending to server (similar to sending)

  expertise – expertise (files on the server, inspection can be checked)

  repeat – re-inspection required

  approval – aprooving

  clientagreement – confirmation by the client is required (if specified in the template, then after the expertise the client needs to "sign" the final version; if it is not required according to the inspection template, then this status is skipped)

  contract – contract (passed verification successfully)

  deny_expertise – did not pass the expertise (refusal during verification)

Works

When a request comes to the server, generated by clicking on the "Submit for verification" button

Coverage

The role of the owner of the webhook is taken into account (who created, that and the owner). Administrators are sent messages about all company inspections. Group Administrators – notification about inspections from those access groups to which the group administrator belongs.

Peculiarities

The system separately records the fact of pressing the "Submit for verification" button. In order for the action to be performed, several criteria must be met, including the completeness of the inspection template. The request "send for verification" comes to the server, as a rule, before the files arrive. However, it is not guaranteed that webhooks will first receive a notification "inspection sent for verification", and only after that a notification about the status change for expertise. Do not build on your side the logic of work, assuming a strict sequence of alerts. She is not strict!

Works

When an inspection is submitted for approval (usually, during a review when a change is made by an expert)

Coverage

The role of the owner of the webhook is taken into account (who created, that and the owner). Administrators are sent messages about all company inspections. Group Administrators – notification about inspections from those access groups to which the group administrator belongs.

Works

At the moment when the inspection is transferred on the server side to the Expertise status

Coverage

The role of the owner of the webhook is taken into account (who created, that and the owner). Administrators are sent messages about all company inspections. Group Administrators – notification about inspections from those access groups to which the group administrator belongs.

Peculiarities

The expertise status is set by the examination by the server when the following criteria are met simultaneously:

• inspection sent by the user for verification

• all inspections files are uploaded to the server

Warning! Inspection can be forced to check through the administrative interface or the integration api even if the above criteria are not met.

Works

When a new user signs up on their own in the mobile application. The notification is sent after the user confirms his phone number or after the user activates, if registration is carried out without confirming the phone number.

Coverage

The role of the owner of the webhook is taken into account (who created, that and the owner). Administrators are sent messages about all new users associated with the administrator's company. Group Administrators – information about new users who, upon registration, are automatically associated with access groups to which the group administrator himself belongs.

Works

When a new user is added to the system, but not as a result of self-registration through the application (there is a separate event for this), but when a user was added through one of the auxiliary interfaces:

• in the web – added by an administrator or someone with sufficient rights,

• via integrapi – software interface for integration,

• share – the user was added as a result of the "Share Inspection" action.

Coverage

The role of the owner of the webhook is taken into account (who created, that and the owner). Administrators are sent messages about all new users associated with the administrator's company. Group Administrators – information about new users who, when created, were bound to access groups to which the group administrator himself belongs.

Peculiarities

The user could be added programmatically (via integrapi) without binding to access groups, then this binding can be set by a separate request. In this case, the group administrator will not receive a notification, but the administrator will receive it.

Works

After the user sends a request to technical support from the mobile application.

Coverage

The role of the owner of the webhook is taken into account (who created, that and the owner). Administrators are sent messages from users associated with the administrator's company. Group Administrators – messages from users who are bound to the same access groups as the group administrator himself (to at least one of the groups).

Peculiarities

So far, very little information is known when contacting support. In fact, when processing such requests, you should rely on the text of the message and who sent it.

Works

When the next GPS point comes to the server from the mobile application AND, the inspection has already been transferred to the expertise or transferred to one of the final statuses

Coverage

The role of the owner of the webhook is taken into account (who created, that and the owner). Administrators are sent messages about all company inspections. Group Administrators – notification about scans from those access groups to which the group administrator belongs.

Peculiarities

Inspection data comes to the server in order: first general metadata, then files, and last of all information from sensors and GPS coordinates. It is assumed that at the time of the transition of the inspection to the expertise status, the GPS coordinates from the application have not yet arrived at the server. You can subscribe to an event in order to receive all received GPS coordinates after the transition from inspection to expertise. A webhook will be called for each arriving point. Including duplicate coordinates. If the inspection is switched to repeat, the webhook will not be called.

The gps_source flag defines the source of coordinates: gps_source: mob – mobile app; gps_source: admin – the administrator set the specified coordinates manually via the web interface.

Works

When changing the inspection template or when creating a new inspection template

Coverage

The current access of the user on whose behalf the webhook was added to the system is taken into account. The data is sent provided that the user has access to the inspection template.

Peculiarities

The event fires both when changes are made and when a new inspection template is created, if it is immediately known that the user who created the webhook has access rights to the inspection template. Changes that increase the version of the inspection template are guaranteed to be logged. For example, editing steps or deleting steps. Not guaranteed, but a webhook can be sent on other inspection template edit events as well. Non-guaranteed changes are considered not critical to the inspection process. For major changes, the inspection template is always upgraded.